|
|
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Agent Li
Galactic Defence Consortium
   |
Posted - 2006.11.29 19:20:00 -
[1]
Also, if you are experiencing stuttering sound, etc.
The problem appears to be centered around AMD dual core processors, and their "relationship" with Windows XP and DirectX.
You can have a temporary workaround by either setting the process to single core in Task Manager for your eve executable
OR
Download
http://www.42productions.de/downloads/ChangeProccessAffinity.zip
Copy it anywhere, such as:
c:\Program Files\ChangeProcessAffinity\
make a desktop shortcut
change the shortcut properties
Target:
"C:\Program Files\ChangeProccessAffinity\ChangeProccessAffinity.exe" "C:\Program Files\dodgy\bin\dodgyprogram.exe" 1
Make sure you have that "1" at the end - that tells it to run on one processor
AND
make sure you replace the "dodgy" with the eve directory and eve executable.
Also check this out:
http://support.microsoft.com/kb/909944/
This last part describes the problem. It is affecting quite a few games.
|
Agent Li
Galactic Defence Consortium
|
Posted - 2006.11.29 19:43:00 -
[2]
 Originally by: Zymm
Edited by: Zymm on 29/11/2006 19:39:58
Its not related to AMD procs. Both of my systems are Intel Core Duo 2.
If you are having the problem, and you have a dual core machine, you need to open Task manager and right click on the process for the eve executable, and set it to single core (single processor).
Microsoft says there is a problem with games that are doing multithreaded timing operations.
|
Agent Li
Galactic Defence Consortium
|
Posted - 2006.11.29 19:50:00 -
[3]
Originally by: duncan senturas
what if im having the issue and i dont have a dual core?
Can't help you there then. This IS a problem with more games than just Eve.
|
Agent Li
Galactic Defence Consortium
|
Posted - 2006.11.29 20:12:00 -
[4]
IF YOU HAVE A DUAL CORE PROCESSOR AND ARE RUNNING WIN XP SP2
TRY THIS FIX
CCP is saying the same thing (except that they are saying use the Task Manager to set to single core).
|
Agent Li
Galactic Defence Consortium
|
Posted - 2006.11.29 20:28:00 -
[5]
This is the same problem that people are having with Serious Sam 2 and Call of Duty 2.
|
Agent Li
Galactic Defence Consortium
|
Posted - 2006.11.29 20:44:00 -
[6]
On examination of the Microsoft bulletin on this problem:
[QUOTE]This problem may occur if the program that you are running uses the QueryPerformanceCounter and QueryPerformanceFrequency functions to generate timecode but uses only the lower 32 bits of the result and assumes that this is a signed number. On hyper-threaded computers, dual-processor computers, or single proc computers in which the CPU speed is greater than 2 GHz, the output may be incorrectly interpreted by certain programs, and as a result, the program may not run correctly or may stop responding.[/QUOTE]
So even if you have a fast single processor CPU, you could be affected.
|
Agent Li
Galactic Defence Consortium
|
Posted - 2006.11.29 21:11:00 -
[7]
Originally by: Nash Wraithwind
Unfortunately I don't think logserver will help you if you're restarting, since you need to save the file to look at it. If the computer is bluescreening before restarting then you could look at the crash dump for an idea of what's going on, but if it's just a restart the problem will likely be quite hard to troubleshoot.
Nash
I'm convinced that this is a multithreading problem. Someone needs to go through the code now and look at how timers are handled.
|
Agent Li
Galactic Defence Consortium
|
Posted - 2006.11.30 14:58:00 -
[8]
If you're going to blame anyone, blame Microsoft for providing a threading model that is making idiotic assumptions about the underlying hardware.
They provide the OS and the libraries to people who write code - who then make the assumption that the threading model is safe.
This is noted in at least TWO Microsoft tech bulletins - even THEY know it's a problem.
It's a problem with Call of Duty 2 - and Microsoft wrote that game.
Sit down for a minute, and stop blaming CCP.
|
|
|
| |
|